Managing virtual machine images in a distributed computing environment

ABSTRACT

Methods, apparatuses, and computer program products for managing virtual machine images in a distributed computing environment are provided. Embodiments includes a management system recording dependencies between the virtual machine images in the image service repository and dependencies between the deployed virtual machines in the compute service and the virtual machine images in the image service repository. Based on the recorded dependencies between the virtual machine images and the dependencies between the deployed virtual machines and the virtual machine images, the management system identifies a virtual machine image that has no deployed virtual machine dependent upon it. Embodiments also include the management system deleting, by the management system, the identified virtual machine image from the image service repository.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of and claims priorityfrom U.S. patent application Ser. No. 14/100,920, filed on Dec. 9, 2013.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, apparatuses, and computer program products for managing virtualmachine images in a distributed computing environment.

2. Description of Related Art

The development of the EDVAC computer system of 1948 is often cited asthe beginning of the computer era. Since that time, computer systemshave evolved into extremely complicated devices. Today's computers aremuch more sophisticated than early systems such as the EDVAC. Computersystems typically include a combination of hardware and softwarecomponents, application programs, operating systems, processors, buses,memory, input/output devices, and so on. As advances in semiconductorprocessing and computer architecture push the performance of thecomputer higher and higher, more sophisticated computer software hasevolved to take advantage of the higher performance of the hardware,resulting in computer systems today that are much more powerful thanjust a few years ago.

Modern computing systems can include a plurality of machines that shareresources with each other. In a distributed computing environment, thereare thousands of resources that can be entrusted in a distributedcomputing environment and accessed as a service. These resources are ofvarious types and often belong to various environments of differenttypes and reside on the hardware of the environment.

SUMMARY

Methods, apparatuses, and computer program products for managing virtualmachine images in a distributed computing environment are provided.Embodiments includes a management system recording dependencies betweenthe virtual machine images in the image service repository anddependencies between the deployed virtual machines in the computeservice and the virtual machine images in the image service repository.Based on the recorded dependencies between the virtual machine imagesand the dependencies between the deployed virtual machines and thevirtual machine images, the management system identifies a virtualmachine image that has no deployed virtual machine dependent upon it.Embodiments also include the management system deleting, by themanagement system, the identified virtual machine image from the imageservice repository.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 sets forth a block diagram of automated computing machinerycomprising an example computer useful in managing virtual machine imagesin a distributed computing environment according to embodiments of thepresent invention.

FIG. 5 sets forth a flow chart illustrating an example method formanaging virtual machine images in a distributed computing environmentaccording to embodiments of the present invention.

FIG. 6 sets forth a flow chart illustrating an additional example methodfor managing virtual machine images in a distributed computingenvironment according to embodiments of the present invention.

FIG. 7 sets forth a flow chart illustrating an additional example methodfor managing virtual machine images in a distributed computingenvironment according to embodiments of the present invention.

FIG. 8 sets forth a flow chart illustrating an additional example methodfor managing virtual machine images in a distributed computingenvironment according to embodiments of the present invention.

FIG. 9 sets forth a flow chart illustrating an additional example methodfor managing virtual machine images in a distributed computingenvironment according to embodiments of the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Example methods, apparatuses, and computer program products for managingvirtual machine images in a distributed computing environment inaccordance with the present invention are described with reference tothe accompanying drawings, beginning with FIG. 1. It is understood inadvance that although this disclosure includes a detailed description oncloud computing, implementation of the teachings recited herein are notlimited to a cloud computing environment. Rather, embodiments of thepresent invention are capable of being implemented in conjunction withany other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (‘SaaS’): the capability provided to the consumeris to use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (‘Paas’): the capability provided to the consumeris to deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (‘IaaS’): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node (10) is only one example of asuitable cloud computing node and is not intended to suggest anylimitation as to the scope of use or functionality of embodiments of theinvention described herein. Regardless, cloud computing node (10) iscapable of being implemented and/or performing any of the functionalityset forth hereinabove.

In cloud computing node (10) there is a computer system/server (12),which is operational with numerous other general purpose or specialpurpose computing system environments or configurations. Examples ofwell-known computing systems, environments, and/or configurations thatmay be suitable for use with computer system/server (12) include, butare not limited to, personal computer systems, server computer systems,thin clients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server (12) may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server (12) may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server (12) in cloud computing node(10) is shown in the form of a general-purpose computing device. Thecomponents of computer system/server (12) may include, but are notlimited to, one or more processors or processing units (16), a systemmemory (28), and a bus (18) that couples various system componentsincluding system memory (28) to processor (16).

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (‘ISA’) bus,Micro Channel Architecture (‘MCA’) bus, Enhanced ISA (‘EISA’) bus, VideoElectronics Standards Association (‘VESA’) local bus, and PeripheralComponent Interconnect (‘PCI’) bus.

Computer system/server (12) typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server (12), and it includes both volatileand non-volatile media, removable and non-removable media.

System memory (28) can include computer system readable media in theform of volatile memory, such as random access memory (‘RAM’) (30)and/or cache memory (32). Computer system/server (12) may furtherinclude other removable/non-removable, volatile/non-volatile computersystem storage media. By way of example only, storage system (34) can beprovided for reading from and writing to a non-removable, non-volatilemagnetic media (not shown and typically called a “hard drive”). Althoughnot shown, a magnetic disk drive for reading from and writing to aremovable, non-volatile magnetic disk (e.g., a “floppy disk”), and anoptical disk drive for reading from or writing to a removable,non-volatile optical disk such as a CD-ROM, DVD-ROM or other opticalmedia can be provided. In such instances, each can be connected to bus(18) by one or more data media interfaces. As will be further depictedand described below, memory (28) may include at least one programproduct having a set (e.g., at least one) of program modules that areconfigured to carry out the functions of embodiments of the invention.

Program/utility (40), having a set (at least one) of program modules(42), may be stored in memory (28) by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystem, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. Program modules (42) generally carry outthe functions and/or methodologies of embodiments of the invention asdescribed herein.

Computer system/server (12) may also communicate with one or moreexternal devices (14) such as a keyboard, a pointing device, a display(24), etc.; one or more devices that enable a user to interact withcomputer system/server (12); and/or any devices (e.g., network card,modem, etc.) that enable computer system/server (12) to communicate withone or more other computing devices. Such communication can occur viaInput/Output (‘I/O’) interfaces (22). Still yet, computer system/server(12) can communicate with one or more networks such as a local areanetwork (‘LAN’), a general wide area network (‘WAN’), and/or a publicnetwork (e.g., the Internet) via network adapter (20). As depicted,network adapter (20) communicates with the other components of computersystem/server (12) via bus (18). It should be understood that althoughnot shown, other hardware and/or software components could be used inconjunction with computer system/server (12). Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment (50)is depicted. As shown, cloud computing environment (50) comprises one ormore cloud computing nodes (10) with which local computing devices usedby cloud consumers, such as, for example, personal digital assistant(‘PDA’) or cellular telephone (54A), desktop computer (54B), laptopcomputer (54C), and/or automobile computer system (54N) may communicate.The cloud computing nodes (10) may communicate with one another. Theymay be grouped (not shown) physically or virtually, in one or morenetworks, such as Private, Community, Public, or Hybrid clouds asdescribed hereinabove, or a combination thereof. This allows cloudcomputing environment (50) to offer infrastructure, platforms and/orsoftware as services for which a cloud consumer does not need tomaintain resources on a local computing device. It is understood thatthe types of computing devices (54A-N) shown in FIG. 2 are intended tobe illustrative only and that computing nodes (10) and cloud computingenvironment (50) can communicate with any type of computerized deviceover any type of network and/or network addressable connection (e.g.,using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment (element 50 in FIG. 2) is shown. Itshould be understood in advance that the components, layers, andfunctions shown in FIG. 3 are intended to be illustrative only andembodiments of the invention are not limited thereto. As depicted, thefollowing layers and corresponding functions are provided:

Hardware and software layer (60) includes hardware and softwarecomponents. Examples of hardware components include mainframes (60A), inone example IBM® zSeries® systems; RISC (Reduced Instruction SetComputer) architecture based servers (60B), in one example IBM pSeries®systems; IBM xSeries® systems; IBM BladeCenter® systems; storage devices(60C); networks and networking components (60D). Examples of softwarecomponents include network application server software (60E), in oneexample IBM WebSphere® application server software; and databasesoftware (60F), in one example IBM DB2®, database software. (IBM,zSeries, pSeries, xSeries, BladeCenter, WebSphere, and DB2 aretrademarks of International Business Machines Corporation registered inmany jurisdictions worldwide).

Virtualization layer (62) provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers(62A); virtual storage (62B); virtual networks (62C), including virtualprivate networks; virtual applications (62D) and operating systems; andvirtual clients (62E).

In one example, management layer (64) may provide the functionsdescribed below. Resource provisioning (64A) provides dynamicprocurement of computing resources and other resources that are utilizedto perform tasks within the cloud computing environment. Metering andPricing (64B) provide cost tracking as resources are utilized within thecloud computing environment, and billing or invoicing for consumption ofthese resources. In one example, these resources may compriseapplication software licenses. Security provides identity verificationfor cloud consumers and tasks, as well as protection for data and otherresources. User portal (64C) provides access to the cloud computingenvironment for consumers and system administrators. Service levelmanagement (64D) provides cloud computing resource allocation andmanagement such that required service levels are met. Service LevelAgreement (SLA) planning and fulfillment (64E) provides pre-arrangementfor, and procurement of, cloud computing resources for which a futurerequirement is anticipated in accordance with an SLA.

Workloads layer (66) provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation (66A); software development and lifecycle management (66B);virtual classroom education delivery (66C); data analytics processing(66D); and transaction processing (66E).

For further explanation, FIG. 4 sets forth a block diagram of automatedcomputing machinery comprising an example computer useful in managingvirtual machine images in a distributed computing environment accordingto embodiments of the present invention. The computer (452) of FIG. 4includes at least one computer processor (456) or ‘CPU’ as well asrandom access memory (468) (‘RAM’) which is connected through a highspeed memory bus (466) and bus adapter (458) to processor (456) and toother components of the computer (452).

Stored in RAM (468) is a management system (499), a module of computerprogram instructions that, when executed causes the computer (452) ofFIG. 4 to provide an image to a virtual machine of a distributedcomputing environment. In the example of FIG. 4, a distributed computingenvironment (430) is created on components of other computers (482). Themanagement system may also be configured to administer provisioning ofvirtual machines, cloud resources, memory, and the like; track customeror user usage of cloud resources; provide a systems management interfacefor configuration of virtual machine environments; and so on.

In the example of FIG. 4, the distributed computing environment includesa compute service (498) which includes deployed virtual machines (497)offered to users of the distributed computing environment (430) as aservice. The distributed computing environment (430) also includes animage service repository (496) that stores images (495) of virtualmachines.

In the example of FIG. 4, the management system (499) may managingvirtual machine images in a distributed computing environment inaccordance with embodiments of the present invention by recordingdependencies between the virtual machine images (495) in the imageservice repository (496) and dependencies between the deployed virtualmachines (497) in the compute service (498) and the virtual machineimages (495) in the image service repository (496). Based on therecorded dependencies between the virtual machine images (495) and thedependencies between the deployed virtual machines (497) and the virtualmachine images (495), the management system (499) identifies a virtualmachine image that has no deployed virtual machine dependent upon it.The management system (499) is also configured to delete the identifiedvirtual machine image from the image service repository.

Also stored RAM (468) of the computer (452) is an operating system(454). Operating systems useful for managing virtual machine images in adistributed computing environment according to embodiments of thepresent invention include UNIX™ Linux™ Microsoft XP™ AIX™ IBM's i5/OS™and others as will occur to those of skill in the art. The operatingsystems (454) and the management system (499) in the example of FIG. 4are shown in RAM (468), but many components of such software typicallyare stored in non-volatile memory also, such as, for example, on a diskdrive (470).

The computer (452) of FIG. 4 includes disk drive adapter (472) coupledthrough expansion bus (460) and bus adapter (458) to the processors(456) and other components of the computer (452). Disk drive adapter(472) connects non-volatile data storage to the computer (452) in theform of the disk drive (470). Disk drive adapters useful in computersfor managing virtual machine images in a distributed computingenvironment according to embodiments of the present invention includeIntegrated Drive Electronics (‘IDE’) adapters, Small Computer SystemInterface (‘SCSI’) adapters, and others as will occur to those of skillin the art. Non-volatile computer memory also may be implemented for asan optical disk drive, electrically erasable programmable read-onlymemory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, aswill occur to those of skill in the art.

The example computer (452) of FIG. 4 includes one or more input/output(‘I/O’) adapters (478). I/O adapters implement user-orientedinput/output through, for example, software drivers and computerhardware for controlling output to display devices such as computerdisplay screens, as well as user input from user input devices (481)such as keyboards and mice. The example computer (452) of FIG. 4includes a video adapter (409), which is an example of an I/O adapterspecially designed for graphic output to a display device (480) such asa display screen or computer monitor. The video adapter (409) isconnected to the processors (456) through a high speed video bus (464),bus adapter (458), and the front side bus (462), which is also a highspeed bus.

The exemplary computer (452) of FIG. 4 includes a communications adapter(467) for data communications with the other computers (482) and fordata communications with the data communications network (400). Suchdata communications may be carried out serially through RS-232connections, through external buses such as a Universal Serial Bus(‘USB’), through data communications networks such as IP datacommunications networks, and in other ways as will occur to those ofskill in the art. Communications adapters implement the hardware levelof data communications through which one computer sends datacommunications to another computer, directly or through a datacommunications network. Examples of communications adapters useful formanaging virtual machine images in a distributed computing environmentaccording to embodiments of the present invention include modems forwired dial-up communications, Ethernet (IEEE 802.3) adapters for wireddata communications, and 802.11 adapters for wireless datacommunications.

The arrangement of computers and other devices making up the exemplarysystem illustrated in FIG. 4 are for explanation, not for limitation.Data processing systems useful according to various embodiments of thepresent invention may include additional databases, servers, routers,other devices, and peer-to-peer architectures, not shown in FIG. 4, aswill occur to those of skill in the art. Networks in such dataprocessing systems may support many data communications protocols,including for example TCP (Transmission Control Protocol), IP (InternetProtocol), HTTP (HyperText Transfer Protocol), WAP (Wireless AccessProtocol), HDTP (Handheld Device Transport Protocol), and others as willoccur to those of skill in the art. Various embodiments of the presentinvention may be implemented on a variety of hardware platforms inaddition to those illustrated in FIG. 4.

For further explanation, FIG. 5 sets forth a flow chart illustrating anexemplary method for managing virtual machine images in a distributedcomputing environment according to embodiments of the present invention.A distributed computing environment refers to a collection of computers,networks, and automated computing machinery configured to performdistributed processing. A non-limiting example of a distributedcomputing environment includes a cloud environment having a virtualizedcomputing platform in which a user may be provided access to computingresources without knowledge, ownership, or physical access to thecomputer resources. The hardware, software, and capabilities of thecomponents of a distributed computing environment or cloud environmentmay be offered to users as services or objects and may generally bereferred to as resources. Non-limiting examples of resources includevirtual machines, processing clusters, host operating systems,applications, processing threads, processing allocations, storageallocations, memory allocations, and any many others as will occur toreaders of skill in the art.

In the example of FIG. 5, the distributed computing environment (530)comprises an image service repository (560) that includes virtualmachine images (562). A virtual machine is a software implementation ofa set of processes or a system. A virtual machine image is an image of avirtual machine. An image service repository is a storage area forstoring the virtual machine images. The distributed computingenvironment (530) of FIG. 5 also comprises a compute service (570) thatincludes deployed virtual machines (572).

The method of FIG. 5 includes the management system (500) recording(502) dependencies (550) between the virtual machine images (562) in theimage service repository (560) and dependencies (552) between thedeployed virtual machines (572) in the compute service (570) and thevirtual machine images (562) in the image service repository (560).Recording (502) dependencies (550) may be carried out by identifyinginformation defining each virtual machine image and comparing it toinformation defining another virtual machine image; using the results ofthe comparison to identify which virtual machine images have sharedinformation; using the identification of virtual machines having sharedinformation and other information, such as timestamps, deployment data,and version number, to determine dependencies between the images; andrecording those determined dependencies.

Recording (502) dependencies (552) may be carried out by identifyinginformation defining each virtual machine image; identifying informationdefining each deployed virtual machine; comparing the informationdefining the virtual machine images and the information defining thedeployed virtual machines to determine which virtual machine images haveinformation in common with a deployed virtual machine; using thedetermination along with other information, such as timestamps,deployment data, and version number, to determine dependencies betweenthe images and the deployed virtual machines; and recording thosedetermined dependencies.

The method of FIG. 5 includes the management system (500) identifying(504) based on the recorded dependencies (550) between the virtualmachine images and the dependencies (552) between the deployed virtualmachines and the virtual machine images, a first virtual machine image(599) that has no deployed virtual machine dependent upon it.Identifying (504) a first virtual machine image (599) that has nodeployed virtual machine dependent upon it may be carried out byexamining the recorded dependencies (550) between the virtual machineimages and the dependencies (552) between the deployed virtual machinesand the virtual machine images to identify a virtual machine image thatis not dependent upon a deployed virtual machine. For example, as willbe explained in greater detail below, the management system (500) mayexamine a hierarchical representation of the recorded dependencies toidentify any virtual machine images not dependent upon a deployedvirtual machine. Identifying (504) a first virtual machine image (599)that has no deployed virtual machine dependent upon it may be carriedout by identifying a virtual machine image that does not depend upon adeployed virtual machine and is not the latest or newest version of aparticular virtual machine. That is, the management system may preservethe latest or newest copy of a virtual machine image.

The method of FIG. 5 also includes the management system (500) deletingthe identified first virtual machine image (599) from the image servicerepository (560). Deleting the identified first virtual machine image(599) may be carried out by destroying the identified virtual machineimage; or sending a message to the image repository service to destroythe identified virtual machine image.

For further explanation, FIG. 6 sets forth a flow chart illustratinganother example method for managing virtual machine images in adistributed computing environment according to embodiments of thepresent invention. The method of FIG. 6 is similar to the method of FIG.5 in that the method of FIG. 6 also includes recording (502)dependencies (550) between the virtual machine images (562) in the imageservice repository (560) and dependencies (552) between the deployedvirtual machines (572) in the compute service (570) and the virtualmachine images (562) in the image service repository (560); identifying(504) based on the recorded dependencies (550) between the virtualmachine images and the dependencies (552) between the deployed virtualmachines and the virtual machine images, a virtual first machine image(599) that has no deployed virtual machine dependent upon it; anddeleting the first identified virtual machine image (599).

In the method of FIG. 6, however, recording (502) dependencies (550)between the virtual machine images (562) in the image service repository(560) and dependencies (552) between the deployed virtual machines (572)in the compute service (570) and the virtual machine images (562) in theimage service repository (560) includes creating (602) a tree datastructure (670). A tree data structure is a data structure thatindicates the dependencies between the virtual machine images and thedependencies between the virtual machine images and the deployed virtualmachines.

In the example of FIG. 6, creating (602) a tree data structure (670)includes creating (604) a node (694, 695, 696) for each deployed virtualmachine (572) in the compute service (570). Creating (604) a node (694,695, 696) for each deployed virtual machine (572) in the compute service(570) may be carried out by storing within the tree data structure (670)a representation of a deployed virtual machine.

In the example of FIG. 6, creating (602) a tree data structure (670)includes creating (606) a node (690, 691, 692, 693, 697, 698) for eachvirtual machine image (562) in the image service repository (560).Creating (606) a node (690, 691, 692, 693, 697, 698) for each virtualmachine image (562) in the image service repository (560) may be carriedout by storing within the tree data structure (670) a representation ofa deployed virtual machine.

In the example of FIG. 6, creating (602) a tree data structure (670)includes connecting (608) the created nodes (690-698) to indicate thedependencies (550) between the virtual machine images (562) in the imageservice repository (560) and the dependencies (552) between the deployedvirtual machines (570) in the compute service (572) and the virtualmachine images in the image service repository. Connecting (608) thecreated nodes (690-698) may be carried out by creating within the treedata structure (670), connections (680, 681, 682, 686) representing thedependencies (550) between the virtual machine images (562); andcreating within the tree data structure (670), connections (683, 684,685) representing the dependencies (552) between the virtual machineimages (562) and the deployed virtual machines (572).

For further explanation, FIG. 7 sets forth a flow chart illustratinganother example method for managing virtual machine images in adistributed computing environment according to embodiments of thepresent invention. The method of FIG. 7 is similar to the method of FIG.5 in that the method of FIG. 7 also includes recording (502)dependencies (550) between the virtual machine images (562) in the imageservice repository (560) and dependencies (552) between the deployedvirtual machines (572) in the compute service (570) and the virtualmachine images (562) in the image service repository (560); identifying(504) based on the recorded dependencies (550) between the virtualmachine images and the dependencies (552) between the deployed virtualmachines and the virtual machine images, a first virtual machine image(599) that has no deployed virtual machine dependent upon it; anddeleting the identified first virtual machine image (599).

The method of FIG. 7 includes the management system (500) identifying(702) based on the recorded dependencies (550) between the virtualmachine images (562) and the recorded dependencies (552) between thevirtual machine images (562) and the deployed virtual machines (572), aparticular virtual machine image (565) within the virtual machinesimages (562) to deploy to a particular virtual machine (575).Identifying (702) a particular virtual machine image (565) within thevirtual machines images (562) to deploy to a particular virtual machine(575) may be carried out by identifying from the dependencies (550, 552)the newest version or last used image for deployment on a virtualmachine. That is, the management system (500) may use the dependencies(550, 552) to select a virtual machine image that best matches the needsof a virtual machine, including the need to have the most up-to-dateimage possible.

Identifying (702) a particular virtual machine image (565) within thevirtual machines images (562) to deploy to a particular virtual machine(575) may be carried out by identifying from the dependencies (550, 552)and based on historical usage, a most used virtual machine image fordeployment on a virtual machine. That is, the management system (500)may use the dependencies (550, 552) and historical usage to select avirtual machine image that best matches the needs of a virtual machine,including the need to have the most used image.

The method of FIG. 7 also includes the management system (500) deploying(704) the identified particular virtual machine image (565) to theparticular virtual machine (575). Deploying (704) the identifiedparticular virtual machine image (565) to the particular virtual machine(575) may be carried out by using the identified particular virtualmachine image to implement the particular virtual machine.

For further explanation, FIG. 8 sets forth a flow chart illustratinganother example method for managing virtual machine images in adistributed computing environment according to embodiments of thepresent invention. The method of FIG. 8 is similar to the method of FIG.5 in that the method of FIG. 8 also includes recording (502)dependencies (550) between the virtual machine images (562) in the imageservice repository (560) and dependencies (552) between the deployedvirtual machines (572) in the compute service (570) and the virtualmachine images (562) in the image service repository (560); identifying(504) based on the recorded dependencies (550) between the virtualmachine images and the dependencies (552) between the deployed virtualmachines and the virtual machine images, a first virtual machine image(599) that has no deployed virtual machine dependent upon it; anddeleting the identified first virtual machine image (599).

The method of FIG. 8 includes the management system (500) receiving(802) from a user (865), a request (850) for a particular virtualmachine image in the image service repository (560). Receiving (802)from a user (865), a request (850) for a particular virtual machineimage in the image service repository (560) may be carried out byreceiving user input requesting a specific virtual machine image.

The method of FIG. 8 also includes the management system (500)suggesting (804) based on the recorded dependencies (550) between thevirtual machine images (562) and the dependencies (552) between thedeployed virtual machines (572) and the virtual machine images (562),another virtual machine image (852) in the image service repository(560) that is dependent upon the particular virtual machine image inresponse to receiving the request (850). Suggesting (804) anothervirtual machine image (852) in the image service repository (560) thatis dependent upon the particular virtual machine image may be carriedout by examining the recorded dependencies (550) between the virtualmachine images (562) and the dependencies (552) between the deployedvirtual machines (572) and the virtual machine images (562) to identifyany newer or more robust versions of the virtual machine image. Forexample, the management system (500) may examine the tree data structure(670) of FIG. 6 to identify any child virtual machine images of thesecond virtual machine image. Suggesting (804) another virtual machineimage (852) in the image service repository (560) that is dependent uponthe particular virtual machine image may also be carried out bypresenting to a user via a graphical user interface, the option ofselecting the suggested other virtual machine image (852).

For further explanation, FIG. 9 sets forth a flow chart illustratinganother example method for managing virtual machine images in adistributed computing environment according to embodiments of thepresent invention. The method of FIG. 9 is similar to the method of FIG.5 in that the method of FIG. 9 also includes recording (502)dependencies (550) between the virtual machine images (562) in the imageservice repository (560) and dependencies (552) between the deployedvirtual machines (572) in the compute service (570) and the virtualmachine images (562) in the image service repository (560); identifying(504) based on the recorded dependencies (550) between the virtualmachine images and the dependencies (552) between the deployed virtualmachines and the virtual machine images, a first virtual machine image(599) that has no deployed virtual machine dependent upon it; anddeleting the identified first virtual machine image (599).

The method of FIG. 9 includes the management system (500) identifying(902) based on the recorded dependencies (550) between the virtualmachine images (562) and the dependencies (552) between the deployedvirtual machines (572) and the virtual machine images (562), a secondvirtual machine image (950) to compress within the image servicerepository (560). Identifying (902) a second virtual machine image (950)to compress within the image service repository (560) may be carried outby identifying an unused virtual machine image that is stored as a fullimage; and identifying a virtual machine image that is stored as a fullimage and is identified as not being an image that the management systemwould recommend to a user (e.g., is not the best or most current imageto use).

Identifying (902) a second virtual machine image (950) to compresswithin the image service repository (560) may also be carried out byidentifying an unused virtual machine image that is stored as a fullimage and is not identified as a candidate for deletion. The managementsystem may identify virtual machines images as candidates for deletionbased on historical usage, priority information, and any other attributeor factor that would occur to readers of skill in the art. A candidatefor deletion may be a virtual machine image that is one of apredetermined number of virtual machine images that are next to bedeleted.

The method of FIG. 9 also includes the management system (500)compressing (904) the identified second virtual machine image (950)including changing the identified second virtual machine image from afull image to a delta image (952). Delta encoding is a way of storing ortransmitting data in the form of differences between sequential datarather than complete files; more generally this is known as datadifferencing. Delta encoding is sometimes called delta compression,particularly where archival histories of changes are required (e.g., inrevision control software). The differences are recorded in discretefiles called “deltas” or “diffs”, after the UNIX file comparisonutility, diff. In situations where differences are small—for example,the change of a few words in a large document or the change of a fewrecords in a large table—delta encoding greatly reduces data redundancy.Collections of unique deltas are substantially more space-efficient thantheir non-encoded equivalents. From a logical point of view thedifference between two data values is the information required to obtainone value from the other. The difference between identical values (undersome equivalence) is often called 0 or the neutral element. Compressing(904) the identified first virtual machine image (950) includingchanging the identified first virtual machine image from a full image toa delta image (952) may be carried out by identifying the differencesbetween the image (950) and another image and only storing theidentified differences.

In a particular embodiment, the management system (500) may also beconfigured to uncompress a virtual machine image or create a new deltaimage to allow for deletion of a virtual machine image. For example, themanagement system (500) may determine that a first delta image is nolonger needed and may apply the first delta image changes to a fullimage that corresponds to the first delta image. In this example, themanagement system (500) may then delete the first delta image. Asanother example, as part of compressing and pruning the virtual machineimages in the image service repository, the management system (500) maycombine multiple delta images together to form a new delta image.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described above with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

1. A method of managing virtual machine images in a distributedcomputing environment, the distributed computing environment comprisingan image service repository that includes virtual machine images, thedistributed computing environment further comprising a compute servicethat includes deployed virtual machines, the method comprising:recording dependencies between the virtual machine images in the imageservice repository and dependencies between the deployed virtualmachines in the compute service and the virtual machine images in theimage service repository; identifying based on the recorded dependenciesbetween the virtual machine images and the dependencies between thedeployed virtual machines and the virtual machine images, by themanagement system, a first virtual machine image that has no deployedvirtual machine dependent upon it; and deleting, by the managementsystem, the identified first virtual machine image from the imageservice repository.
 2. The method of claim 1 wherein recordingdependencies between the virtual machine images in the image servicerepository and dependencies between the deployed virtual machines in thecompute service and the virtual machine images in the image servicerepository further comprises creating a tree data structure including:creating a node for each deployed virtual machine in the computeservice; creating a node for each virtual machine image in the imageservice repository; and connecting the created nodes to indicate thedependencies between the virtual machine images in the image servicerepository and the dependencies between the deployed virtual machines inthe compute service and the virtual machine images in the image servicerepository;
 3. The method of claim 1 further comprising: identifyingbased on the recorded dependencies between the virtual machine imagesand the dependencies between the deployed virtual machines and thevirtual machine images, by the management system, a particular virtualmachine image within the virtual machines images to deploy to aparticular virtual machine; and deploying, by the management system, theidentified particular virtual machine image to the particular virtualmachine.
 4. The method of claim 1 further comprising: receiving from auser, by the management system, a request for a particular virtualmachine image in the image service repository; and in response toreceiving the request, suggesting based on the recorded dependenciesbetween the virtual machine images and the dependencies between thedeployed virtual machines and the virtual machine images, by themanagement system, another virtual machine image in the image servicerepository that is dependent upon the particular virtual machine image.5. The method of claim 1 further comprising: identifying based on therecorded dependencies between the virtual machine images and thedependencies between the deployed virtual machines and the virtualmachine images, by the management system, a second virtual machine imageto compress within the image service repository; and compressing, by themanagement system, the identified second virtual machine image includingchanging the identified second virtual machine image from a full imageto a delta image.
 6. The method of claim 5 wherein the delta imageindicates the difference between the second virtual machine image andanother virtual machine image it is dependent upon. 7-20. (canceled)